Practical Software Development Techniques by Tools & Techniques for Building Enterprise Software

Author:Tools & Techniques for Building Enterprise Software
Format: epub

The Scrum Master may record these answers to keep a running log of work done and work remaining. Any impediments should be resolved by the Scrum Master; the team concentrates on completing the tasks in the sprint backlog.

So how is progress measured? Completed items are plotted against time in a graph known as a “burndown chart.” This allows for comparison of the number of items remaining versus time and can be done on a sprint level and the overall project level. Backlog items or sprint story points are always on the vertical graph; it may be easier to visualize story points. The horizontal axis is time, either number of sprints for the project burndown, or days for a sprint burndown. For a sprint the progress is tracked after each daily scrum. So for example, if the team committed to 32 story points for a particular sprint the first plot point would be day one of the sprint with a marker on the vertical axis at 32. After the next daily scrum, if the team completes 3 story points the marker would be at 29. For day three, two completed points would put the marker at 27, and so on. Ideally on day 30 (or the last day of the sprint) the marker is at zero, meaning that all work was completed as of the last day of the sprint. A sample sprint burndown chart is shown below in Figure 6-3. A little over halfway through does the sprint appear to be on track?

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.